Micron Document




Object-oriented user interface
part 4/8 · 11.3 KB total
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Many futuristic imaginings of user interfaces rely heavily on OOUI and especially OOGUI concepts.cite-ref-4[4] However there are many examples of user interfaces that implement one or more of those other ideas, but which are not in fact OOUIs - though they are often wrongly labelled as OOUIs.cite-ref-constantine-5-0[5] Conversely, there are examples of OOUIs that are neither graphical, nor employ direct manipulation techniques, nor employ strong metaphors. For example, the earliest versions of the Smalltalk programming language had a command line interface that was nonetheless also clearly an OOUI,cite-ref-kay-6-0[6] though it subsequently became better known for its pioneering role in the development of GUIs, direct manipulation and visual metaphors.

Relationship to object-oriented programming

Although there are many conceptual parallels between OOUIs and object-oriented programming, it does not follow that an OOUI has to be implemented using an object-oriented programming language.

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────